HaCKeRz Kr0nlcKLeZ 1

home *** CD-ROM | disk | FTP | other *** search

/ HaCKeRz Kr0nlcKLeZ 1 / HaCKeRz Kr0nlcKLeZ.iso / scriptz / pmr40.exe / VERSIONS.TXT < prev

Wrap

Text File | 1997-03-17 | 17.4 KB | 373 lines

This is the versions file for the Protection MASTER Script version 4. A copy of the contents of this file can be found on the official web page for the script, located at http://www.iinet.net.au/~ventura/protect.html. Updates will always appear on that page first. 17/03/97 * Fixed a bug or two relating to the unsetting of the variables used to determine repeating flood. * Edited the clone kick (when the limit is exceeded on join) to a 30 second ban instead of a permanent ban. * Moved the Private sound flood to the channel flood protection popups, and renamed this to Channel sound flood, having been convinced that it does have more to do with channel flood than private flood. 16/03/97 * Been looking around for a professional windows installer, but I didn't really find anything that allowed me to distribute the script using that version. The installation will end up being extremely simple anyway. * Fixed up an error in the on kick routine, and cleaned up the on deop routine. * Edited the silence ban kick routines to include a 'devoice' in case the user in question is voiced instead of being opped. 15/03/97 * Almost finished the help file. * Fixed the away message storer with regards to people not being on a channel you're on. It now records messages received from them, and replies with the standard "I am away" notice. 14/03/97 * Fixed a few bugs. One was with the script not effectively protecting against a clone having been kicked. I never noticed before, because a ban usually accompanies a kick, and that would trigger protection. This is now fixed, so anyone who kicks your clone is in for a shock. Another bug fix was with being able to add a clone to the userlist; of course, there is no need to do this (unless your clone's userid is different), so I've added a check to make sure. Thanks to DaWabbit for helping me pick up on these. * Improved the editing of the channel mode change protection setting. From now, no unknown modes can be entered (eg. trying to set a mode of +ac or -f). This routine also checks for invalid entries of more than one word, and it checks the minus modes against the plus modes to ensure that no settings are the same. I'd like to think that the entire routine for changing the mode is now 'idiot' proof :) * Added an option to turn on or off the script's auto-pinger. If you turn it off, when people enter 'ping me' in a channel you have ops on, it'll ignore it. 13/03/97 * Got through a lot more of the help file... * Fixed up voting flood protection, so it acts in the same way as the flood protection routines for everything else. This script now uses no user levels whatsoever; everything is made up of text files and variables :) * Fixed up errors in the offensive word protection routines, and renamed to the unallowed text protection. Any combination of words can be added to this list now, so it can effectively cover swearing, advertising, and ops begging...for example, if I wanted to add advertising protection to the unallowed text protection, I could add certain strings like "join #" and "come to #" to the list, and it will kick if that is detected. With this sort of customisability available, there is no limit to what uses you can put this to. Admittedly, you don't get specific kick messages like "Advertising detected", but that is a small price to pay for such a routine. * Fixed the offensive nick protection to not allow submissions of more than one word. Nicks themselves can only be made up of one 'word' anyway, so there is no problem with this. 12/03/97 * Fixed the editing of the away timers. The input now is in minutes instead of seconds, which makes it a lot easier to edit. This covers both the timer for the auto-away and the timer for the displaying of the away message in all channels. * Most of the testing seems to be coming along well. * Coded topic lock protection. It's an instant thing that will always boot up disabled, but is added via the channel window popups. You can choose to have superops immune to the topic lock, with varying 'punishments', notably nothing, deop and KickBan, on an attempted topic change. 11/03/97 * Been doing a lot of testing recently... * ...And writing the help file :) * Fixed up the 'ping me' auto-pinger. It was pinging people with 'ping me' anywhere in $parms, without $parms being just 'ping me' 8/03/97 * Added mass devoice protection to the mass mode list. * Started seriously writing the help file. * Made a couple of changes to the dcc flood protection, the nick change flood protection, and the join/part flood protection. The nick change and join/part flood protection now count up independently of the text flood protection. Suppose text flood protection works on 5 in 10 seconds, and four have been received...then the person changes nick. Normally that would bung it up to 5 and perform the kick, but becasue it's nick change flood, that doesnt happen now. This means that the two default levels for nick change and join/part flood will be lowered considerably, to something like 3 in 5 seconds. The dcc flood protection now works on a user by user basis, instead of as a whole, so ignores are user specific, and any privatekick setting will now trigger it off. * I'll start testing pretty heavily shortly. Damn, I haven't even TRIED the dcc text flood protection as yet, let alone a lot of other things. This is the hard part (along with writing that damn help file). Don't listen to what anyone else says; the coding is the easy bit :) 7/03/97 * Added the option to view the current stats in the status window, or open up an individual window to view them in. It will default to displaying in the individual window.. * Added an auto-join list. It's merely a list of channels that the script will attempt to join (assuming auto-join is turned on) during the startup. Channels can be added and removed via the channel window popups. 6/03/97 * Changed the format of the popups. The menus for editing the current channel and private-related settings will be found in the status window popups and the titlebar popups, whilst the channel window popups will host the channel-specific, and immediate irc-related options, such as performing scans, setting away/back, voting and topic/mode changes. * Edited the offensive nick protection, and coded an offensive word protection to the script. Both work in the same way; you add a word to the list of either, and it is checked in ppl's text and their nicks (channel text only), with a suitable punishment to follow if the word is found present :) This list of words is stored in text files, so editing the list is easy to do. Both start out empty. * Moved all the files to read from the /settings directory, from the mirc home directory. I did this because, what with the addition of the two files used to store the offensive nicks and the offensive words (above), the txt file count is getting a bit too large. This script will therefore come packaged in a zip (within the main zip) that will take a "pkunzip -d filename.zip" to open it correctly. * Coded an emergency key. Pressing F10 will enable all of your private flood protection at very sensitive settings, disable immunity and enable your private kicking option. Use this if you have fairly lenient settings, and all of a sudden, something big happens...or perhaps, for that super op who's suddenly turned against you. 5/03/97 * Added an auto-pinger. You have to type 'please ping me' in a channel to have the script ping you, and a notice is returned informing of how long it took. * Started coding the simple popups. This was done to acommodate either the newbies who might get their hands on this thing, or the ppl who merely wish to have a more 'instant' access to a wide range of options (ie. being able to turn all of the channel flood protection off in one go, for example). 4/03/97 * Worked on the away/back system nearly all day. The auto-away system now doesn't have an 'auto-return' system....ie, you have to manually return (as you would from being normally away). This doesn't seem to be of any consequence tho. The nick now defaults to not changing (as was with 3.25) when you're away, but a customised away nick can be easily configured. Messages can be left for you when away, either by page (normal method) or by the MSGLogger, both of which can be on or off. Both are written to file with a prefix of either 'page' or 'msg'. Upon receipt of an msg, the window containing the message is removed. The mirc titlebar changes format when away to display the number of pages and messages that have been received in that time. The timer lengths for the auto-idle timer and the away message timer can be changed (both default at 600 seconds, equivalent to 10 minutes). * Added an option to turn the auto-opping for super ops on or off (requested). This does just that, so if a super op has been deopped, for example, the script will still seek to re-op that person. * Worked on more of the popups. 3/03/97 * Completed a couple of the popups, but this wasn't achieved without running out of space in the aliases file. I fixed this by moving an alias or two directly to the locations that trigger it, freeing up space in the aliases file in the process. Now all the current settings can be viewed via the function keys F5-F9.. * Fixed (I hope) the away/back routine not doing the wrong things, in particular, concerning the idle away options. Things like returning from a long amount of time away, to have the idle-away automatically cut in, and set me as away again. Annoying.. * Added an option to change the severity of a punishment when having flooded. Despite having been on irc for probably well over a year, I only just learnt today that, if a non-op on a channel is banned, they cannot speak in the channel. It's effectively a less 'forceful' way to stop a flood occuring, so there is now the option to have all channel text floods merely ban the flooder (and a deop if they're an op at the time). This doesn't work on floods like join/part flood and nick change flood, of course, because you don't need to be able to speak to do those things. In both cases, there is also the option to edit the ban timer length. * Decided that I'll probably scrap swearing protection, and perhaps ops begging and advertising protection...not sure as yet. 2/03/97 * Fixed up the date for yesterday...bloody February, always does that to me!! :) * Coded the private text checking routines: CAPS, repeating, length flood and colour. This had also already been coded for the public area (don't think I mentioned that). * Ran out of space in the normal channel popup area, so I severed the popups files into two, and an easy command can be used to switch between them. It essentially seperates the channel protection options and the private protection options, with everything else being in both. * Coded dcc text flood protection. On dcc the text checking flood protections, it looks to the private settings for these, and uses them. * Coded invite flood protection. Option to do nothing, put the person on a 30 second invite ignore, or kick the user (if possible) from any channel that you can. 1/03/97 Thanx to a cool change, and my enthusiasm, I've spent the whole day getting stuck into it...progress has been unbelievable. This is what I got up to: * Added the set/away back function to the script. This time round, the script defaults to adding '-Away' on to the end of your normal nick, while you're away. There is also the option to customise an away nickname if you wish, since not all irc networks support long nicknames, and the addition of -Away to the end of your normal nick might take it over the length limit. The script also updates the /away message every 5 minutes, so that people initiating a /whois on you can see for themselves roughly how long you've been away. * Added an auto idle away to the script. The timer length can be changed; it defaults to 10 minutes (600 seconds). The option can also be enabled to private automatic return (when the computer senses that you have returned) or manual return (you have to initiate the return yourself manually - as you would with being normally away). Doing all this caused a few problems with the normal away/back routine, but I think they were all fixed. As usual, I haven't run as many tests as I would have liked to. * Coded private msg (including actions) and notice flood protection. As is usual, with the other options, you can set how many times this must happen, and in how many seconds, to set off the protection. * Coded the 'kicking on private flood' option. Note that this does not happen on attempted ctcp or dcc send/chat floods, since the coding used to monitor how many ctcp's have been received is not user-specific. * Pretty much cutted and pasted the clone scan, stats display, ircop scan and the voting feature to 4.0alpha. These all seemed to be functioning flawlessly from 3.25final, so there was nothing that needed to be worked on. I *may* consider integrating an 'undecided' option into the voting feature. * Coded a couple of the 'View current settings' aliases (F5 and F6), that relate to the current settings of the popups around them (you'll understand what I mean when you see it). * Several other things... Work still on the 'to be done' list includes: Viewing the current settings, ops begging, swearing and advertising protection, text checking private protection (repeating, colour, CAPS and length flood), DCC text flood prot, invite flood protection, notice options, current topic protection options, DALnet popups, and a simple/advanced popups switch for those who are either new or who would just prefer a less complex way of managing all these protections. Once all this is done, I'll be in testing mode for a week or two, fixing all the bugs no doubt I'm gonna find, and writing an extensive help file. Then, after all this hard work, I'll decide whether I'm still prepared to just 'give it away'... 28/02/97 * Coded mode change protection. You can set exactly what plus modes and minus modes you want, including a specific key setting and a numerical limit. The default setting will be +tn-k. 27/02/97 * Not as much work is being done at the moment as I'd like to, because of a heat wave we're experiencing. It's been very, VERY hot and humid, and it makes coding extremely difficult. I'm doing the best I can, but you're going to have to bear with me for a few days, until it cools. 26/02/97 * Enhanced the on op, deop, kick and ban routines. They now incorporate mass mode protection, in a way similar to the new code that handles normal flood protection. As before, you will be able to edit how many times it must happen in how many seconds, so the sensitivity can be easily modified. I wanna run more tests on these routines before I move on tho :) * The mass deop, op, kick and ban routines seem to work fine, but not nearly enough testing has gone into them for my liking. It's still early days yet tho. 24/02/97 * At the moment, the new version has the following features :- * 4 user levels - Super ops, voiced users, denied ops and a shitlist. People have expressed to me their desire for a voiced list, and I decided to add that in place of the normal op list. There is now also the option to add a user by generic IP or by static IP to the user list, instead of the generic default. I know a couple of people who have static IP's, so this seems to be a good idea. By the way, from now on, the shitlist does not have customisable shitlist messages, like there were with 3.25final. For myself, at least, it was an unnecessary option that I never took advantage of. * Channel text flood, join/part flood and nick change flood have all been coded (the detection routine is completely different now - IMHO it is much better than before). The sensitivity can be easily adjusted now...if you want the text flood protection to kick if there have been 7 lines of text in 10 seconds, for example, that can be changed easily. * From version 4 onwards, there will be no home channel, as such. All settings will come into play for all channels that you have ops on. This will free up a lot of coding space, which was the main problem encountered with version 3. * At present, the options surrounding immunity, clone on-join detection, script revenge, mass-deop protection, offensive nick, ircop join, and super-ops-can-only-op have been coded. Most of these work pretty much the same as, or better, than they did with version 3. 23/02/97 * Started work on the Protection MASTER version 4.0alpha. Despite the 3.25 final, this version is being designed from scratch.